Traceability system

ABSTRACT

An individual article management system for managing an individual article distributed through a plurality of sites with a form thereof changed at least one of the plurality of sites. Each of the information processing apparatuses transmits read identification information and formed index data to a data center apparatus through a network, and the data center apparatus, receives the transmitted identification information and the transmitted index data, and stores each of the received index data into a storing apparatus so as to be associated with each other on the basis of the identification information for identifying the individual article.

CROSS REFERENCE TO RELATED APPLICATION

This is a continuation of U.S. application Ser. No. 11/645,565, filedDec. 27, 2006, which is a continuation of U.S. application Ser. No.11/060,563, filed Feb. 18, 2005 (now U.S. Pat. No. 7,183,923). Thisapplication relates to and claims priority from Japanese PatentApplication No. 2004-043831, filed on Feb. 20, 2004. The entirety of thecontents and subject matter of all of the above is incorporated hereinby reference.

BACKGROUND OF THE INVENTION

The present invention relates to a technique for realizing traceabilityof individual articles cutting across a plurality of enterprises.

As a technique for managing and grasping distribution situations ofindividual articles, the technique disclosed in JP-A-2000-233808 hasbeen known. In the document, IDs are assigned to individual articles,the IDs are read at each site, and information thereof is managedcollectively, whereby individual articles can be traced. By writing theID in an RFID tag, articles can be traced on an individual basis even ifthey are packed in boxes or the like.

SUMMARY OF THE INVENTION

In the document, although IDs are assigned to individual articles, theycan no longer be traced if they are processed in an enterprise and theirIDs are changed.

IDs are assigned to individual articles, and information of movement ofindividual articles across enterprises is collectively managed. If theID is changed in an enterprise, information for relating the pre- andpost-change IDs to each other is managed. Particularly, informationprocessing is carried out to cope with a change in form of individualarticles.

The present invention includes use of tags attached to individualarticles for coping with a change in form of individual articles. Thetags include rewritable IC tags and read-only IC tags. Moreover, thepresent invention includes assimilating a difference between ID systemsused by (computer systems used by) parties involved in distribution. Itincludes, for example, exchanging information at a center apparatusconnected via a network to the computer system of each party involved indistribution. This can be equally applied to the case where data formatsof tags are different. The present invention includes assimilating adifference between tags used by parties involved in distribution isassimilated. If read-only tags and rewritable tags coexist, for example,rewritable tags are subjected to processing same as that for read-onlytags. That is, control for prohibition of writing is performed.

The present invention includes storing unique IDs for identifying tagsthemselves in tags capable of storing information.

The present invention includes providing an output indicating thatattached tags should be changed to computers installed at sites ifdivergence/integration of individual articles is detected. If theindividual article is diverged into two articles, for example, displayindicating that one or two new tags should be attached is output to ascreen. If two individual articles are integrated into one article, anoutput indicating that one tag should be discarded is provided. Ifindividual articles are integrated, a flag may be set in the centerapparatus with one tag as being active (i.e. for use in subsequentdistribution processes). In this case, the present invention includesmaking the non-active tag active if divergence is detected for the tag.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an inter-business traceability system;

FIG. 2 is a block diagram of the inter-business traceability system ofthe present invention;

FIG. 3 shows an embodiment when the present invention is applied to themeat industry;

FIG. 4 is a flowchart showing a flow of a process for collecting datawhen the present invention is applied to the meat industry;

FIG. 5 is a flowchart showing a flow of a process using data collectedwhen the present invention is applied to the meat industry;

FIG. 6 is a block diagram showing an embodiment when the presentinvention is applied to the meat industry;

FIG. 7 shows one example of process history data created at sites if theID of a trace object is changed and the date and time across sites isnot correct when the present invention is applied to the meat industry;

FIG. 8 shows one example of process history data which is managed at atraceability data center when the present invention is applied to themeat industry;

FIG. 9 is one example of index data which is managed at the traceabilitydata center when the present invention is applied to the meat industry;

FIG. 10 is a flowchart showing a flow of a process for creating data atsites if the ID of a trace object is changed and the date and timeacross sites is not correct when the present invention is applied to themeat industry;

FIG. 11 is a flowchart showing a flow of a process for collecting dataat the traceability data center if the ID of a trace object is changedand the date and time across sites is not correct when the presentinvention is applied to the meat industry;

FIG. 12 is a flowchart showing a flow of a process using data collectedif the ID of a trace object is changed and the date and time acrosssites is not correct when the present invention is applied to the meatindustry;

FIG. 13 is a flowchart showing a flow of a process using data collectedif no index data is required when the present invention is applied tothe meat industry;

FIG. 14 shows individual article information A; and

FIG. 15 shows traceability information.

DESCRIPTION OF THE EMBODIMENTS

Embodiments of the present invention will be described in detail below.

Trace-back which is realized by implementing the present inventionrefers to knowing locations and times at which an object existed on itsway, and locations and times at which components of the object existedon their way. Trace-forward which is realized by implementing thepresent invention refers to knowing locations and times at which theobject existed on its way and a location at which the object currentlyexists, and locations and times at which a product obtained byprocessing the object existed on its way and a location at which theproduct currently exists.

Objects which are traced by implementing the present invention includefoods, medical products, apparel products, electronic devices, parts andraw materials, which may be packed. Packed boxes and the like may alsobe objects to be traced. Locations that are traced are called sites. Thesite is, for example, a production plant, processing plant, distributioncenter, wholesale center, retail store or consumer, and may be, forexample, a plurality of branches of the wholesale center. A data carriersuch as a barcode or RFID having UCC/EAN-128, a slip number and anarbitrary number (hereinafter referred to as ID) written therein isattached or related to the trace object. The ID of the trace object maybe changed as a result of integrating the trace object with one or moreother trace objects at a processing plant or the like, dividing thetrace object into two or more trace objects, packing one or more traceobjects in one box and shipping the same, or taking out one or moretrace objects from a received box.

One example of the configuration of an inter-business traceabilitysystem of the present invention is shown in FIGS. 1 and 2. Theinter-business traceability system comprises a traceability data center,one or more sites, and networks such as a telephone line, a LAN and adedicated line. The traceability data center collects informationrequired for traceability from the site and outputs trace-backinformation and trace-forward information, and comprises an externalstorage device such as a hard disk, communication devices such as amodem, a router and a terminal adapter, a central processing unit suchas a CPU, and output devices such as a display, a printer, a FAX and anelectronic data output, and may comprise input devices such as akeyboard, a mouse and a scanner as shown in FIG. 2. The site i (1≦i≦n)manages individual articles of the trace object during receipt/shipmentand processing, and comprises communication devices such as a modem, arouter, a terminal adapter and a FAX, receipt/shipment data creatingmeans and index data creating means, and may comprise an externalstorage device such as a hard disk and a central processing unit such asa CPU like the site shown in FIG. 2. The traceability data center andthe site i (1≦i≦n) are connected to each other using the communicationdevices.

The receipt/shipment data creating means reads the ID written in thebarcode or RFID attached to the trace object by a reader when the traceobject is received at and is shipped from the site, createsreceipt/shipment data, and sends the receipt/shipment data to thetraceability data center via the communication device. Alternatively,the receipt/shipment data creating means may connect to areceipt/shipment managing system such as a WMS or ERP system, createreceipt/shipment data from information when the trace object of the siteis received at and shipped from the site, and send the receipt/shipmentdata to the traceability data center via the communication device.

The receipt/shipment data is data indicating when and from which site towhich site the trace object was received or shipped, and has informationincluding IDs for identifying individual articles, the date and time ofreceipt or shipment, the site name, the name of the receipt/shipmentdestination, and the name of a process for distinguishing betweenreceipt and shipment.

The index data creating means reads IDs written in barcodes or RFIDsattached to the pre-change and post-change trace objects by a readerwhen the ID is changed as a result of processing or packing the traceobject in the site, creates index data, and sends the index data to thetraceability data center via the communication device. Alternatively,the index data creating means may connect to a production managingsystem such as a WMS, MES or BOM system, create index data frominformation when the ID of the trace object is changed in the site, andsend the index data to the traceability data center via thecommunication device. Alternatively, as in the site m shown in FIG. 2,the index data creating means may connect to the production managingsystem such as a WMS, MES or BOM system, create index data frominformation when the ID of the trace object is changed in the site m,store the index data in the external storage device of the site m, andsend the index data to the traceability data center via thecommunication device upon request from outside. The index data is dataindicating the relation of the ID before a process of the trace objectin the site such as processing or packing with the ID after the process,and has information including the ID before the process, the ID afterthe process, and the names of processes such as processing, integration,division, packing and unpacking.

When the trace object is received at the site, the receipt/shipment datacreating means reads the ID of the trace object, adds thereto thereceipt/shipment date and time, the site name, the name of thereceipt/shipment destination and the name of the process to createreceipt/shipment data, and sends the receipt/shipment data to thetraceability data center via the communication device. The centralprocessing unit of the traceability data center stores thereceipt/shipment data in the external storage device. In the site, theindex data creating means reads the ID before the trace object isprocessed, reads the ID after the processing of the trace object, addsthe name of the process to the IDs before and after the processing, andsends them to the traceability data center via the communication device.The central processing unit of the traceability data center stores theindex data in the external storage device. When the trace object isshipped from the site, the receipt/shipment data creating means readsthe ID of the trace object, adds thereto the receipt/shipment date andtime, the site name, the name of the receipt/shipment destination andthe name of the process to create receipt/shipment data, and sends thereceipt/shipment data to the traceability data center via thecommunication device. The central processing unit of the traceabilitydata center stores the index data in the external storage device. Thecentral processing unit of the traceability data center reads thereceipt/shipment data and index data stored in the external storagedevice, and links thereto related data, whereby trace-back informationand trace-forward information of the trace object can be output via theoutput device.

For means for sending receipt/shipment data and index data from the siteto the traceability data center, data may be sent directly, input usinga Web browser, stored in a file format and sent in a file, or sentthrough FAX. In the case of sending data through FAX and the like,receipt/shipment data and index data created at the site may be inputfrom the input device of the traceability data center as shown in FIG.2. For timing of sending receipt/shipment data and index data from thesite to the traceability, the data may be sent immediately after thedata is created, at fixed intervals, or when the data is accumulated ina fixed amount. As shown in the site m in FIG. 2, the created index datamay be stored in the external storage device of the site m, and not sentunless the send of the data is requested by the traceability datacenter. The central processing unit of the traceability data centerreads the index data from the external storage device of thetraceability data center, the external storage device of the site orboth, and creates and outputs trace-back or trace-forward information.When the central processing unit of the traceability data center readsthe index data from the external storage device of the site, the readindex data is stored in the external storage device of the traceabilitydata center, and the index data may be read from the external storagedevice of the traceability data center for second and subsequent times,or a period over which the index data is stored in the external storagedevice of the traceability data center is set, and the index data storedin the external storage device of the traceability data center may bedeleted after expiration of the period.

In this example, an embodiment for implementing the present inventionwill be described where the ID related to the trace object is not fixed,but changed through a production or distribution process. In thisexample, as shown in FIG. 3, the trace object is a meat, and the sitesare a plurality of producers (A, B, C, D) feeding beef cattle, aplurality of processors (A, B, C, D) dressing beef cattle into cutmeats, a plurality of wholesalers (A, B, C, D) assorting cut meats forretailers, a plurality of retailers (A, B, C, D) processing a pluralityof cut meats together into ground meats, and many and unspecifiedconsumers consuming ground meats. At the producer A, beef cattle havingattached thereto a tag with the ID of 100 is shipped to the processor B.At the processor B, the beef cattle with the ID of 100 is received fromthe producer A, and dressed to produce two cut meats, tags with IDs of1001 and 1002 are attached to the cut meats, respectively, the cut meatwith the ID of 1001 and the cut meat with the ID of 1002 are packed in abox having attached thereto a tag with the ID of 501, and the box withthe ID of 501 is shipped to the wholesaler C. At the wholesaler C, thebox with the ID of 501 is received from the processor B, a tag with theID of 310 is attached to the box with the ID of 501 for the purpose ofassortment, and the box with the ID of 301 is shipped to the retailer D.At the retailer D, the box with the ID of 310 is received from thewholesaler C, the two cut meats having attached thereto the tags withIDs of 1001 and 1002 are taken out from the box with the ID of 310, thecut meat with the ID of 1001 and the cut meat with the ID of 9001 areprocessed together to produce one ground meat, a tag with the ID of11-111 is attached to the ground meat, and the ground meat with the IDof 11-111 is shipped to the consumer. The consumer receives the groundmeat with the ID of 11-111 from the retailer D.

A flow of a process of receipt/shipment data creating means and indexdata creating means at sites of the producer A, the processor B, thewholesaler C and the retailer D is shown in FIG. 4.

The tracing of the beef cattle with the ID of 100 is started from theproducer A (step 1000). The receipt/shipment data creating means of theproducer A reads the ID of the beef cattle being a shipped article (step1010).

The receipt/shipment data creating means of the producer A createsreceipt/shipment data with the number 100 input for the ID, a shipmentdate and time input for the date and time, the producer A input for thesite name, the processor B input for the receipt/shipment destinationand shipment input for the process (step 1011).

The receipt/shipment data creating means of the producer A sends thecreated receipt/shipment data to the traceability data center. Thecentral processing unit of the traceability data center stores thereceived receipt/shipment data in the external storage device (step1012).

The beef cattle with the ID of 100 is received at the processor B (step1100).

The receipt/shipment data creating means of the processor B reads the IDof the beef cattle being a received article (step 1101).

The receipt/shipment data creating means of the processor B createsreceipt/shipment data with the number 100 input for the ID, a shipmentdate and time input for the date and time, the processor B input for thesite name, the producer A input for the receipt/shipment destination andreceipt input for the process (step 1102).

The receipt/shipment data creating means of the processor B sends thecreated receipt/shipment data to the traceability data center. Thecentral processing unit of the traceability data center stores thereceived receipt/shipment data in the external storage device (step1103).

The index data creating means of the processor B reads the ID of thebeef cattle before the beef cattle is dressed (step 1104).

The index data creating means of the processor B attaches tags with IDsof 1001 and 1002 to two cut meats obtained by dressing the beef cattle(step 1105).

The index data creating means of the processor B creates index data withthe number 100 input for the pre-dressing ID (Before), the numbers 1001and 1002 input for the post-dressing ID (After), and dressing input forthe process, and stores the index data in the external storage device ofthe processor B (step 1106).

The index data creating means of the processor B reads IDs of the twocut meats with IDs of 1001 and 2001 before the cut meats are packed(step 1107).

The index data creating means of the processor B attaches a tag with theID of 501 to a box packed with the two cut meats (step 1108).

The index data creating means of the processor B creates index data withnumbers 1001 and 2001 input for the pre-packing ID (Before), the number501 input for the post-packing ID (After), and packing input for theprocess, and stores the index data in the external storage device of theprocessor B (step 1109).

The receipt/shipment data creating means of the processor B reads the IDof the box being a shipped article (step 1010).

The receipt/shipment data creating means of the processor B createsreceipt/shipment data with the number 501 input for the ID, a shipmentdate and time input for the date and time, the processor B input for thesite name, the wholesaler C input for the receipt/shipment destination,and shipment input for the process (step 1011).

The receipt/shipment data creating means of the processor B sends thecreated receipt/shipment data to the traceability data center. Thecentral processing unit of the traceability data center stores thereceived receipt/shipment data in the external storage device (step1012).

The box with the ID of 501 is received at the wholesaler C (step 1200).

The receipt/shipment data creating means of the wholesaler C reads theID of the box being a received article (step 1201).

The receipt/shipment data creating means of the wholesaler C createsreceipt/shipment data with the number 501 input for the ID, a receiptdate and time input for the date and time, the wholesaler C input forthe site name, the processor B input for the receipt/shipmentdestination, and receipt input for the process (step 1202).

The receipt/shipment data creating means of the wholesaler C sends thecreated receipt/shipment data to the traceability data center. Thecentral processing unit of the traceability data center stores thereceived receipt/shipment data in the external storage device (step1203).

The index data creating means of the wholesaler C reads the ID of thebox before another tag for assortment is attached (step 1204).

The index data creating means of the wholesaler C attaches a tag with anID to the box for assortment (step 1205).

The index data creating means of the wholesaler C creates index datawith the number 501 input for the preceding ID (Before), the number 310input for the subsequent ID (After), and assortment input for theprocess, and stores the index data in the external storage device of thewholesaler C (step 1206).

The receipt/shipment data creating means of the wholesaler C reads theID of the box being a shipped article (step 1010).

The receipt/shipment data creating means of the wholesaler C createsreceipt/shipment data with the number 310 input for the ID, a shipmentdate and time input for the date and time, the wholesaler C input forthe site name, the retailer D input for receipt/shipment destination,and shipment input for the process (step 1011).

The receipt/shipment data creating means of the wholesaler C sends thecreated receipt/shipment data to the traceability data center. Thecentral processing unit of the traceability data center stores thereceived receipt/shipment data in the external storage device (step1012).

The box with the ID of 310 is received at the retailer D (step 1300).

The receipt/shipment data creating means of the retailer D reads the IDof the box being a received article (step 1301).

The receipt/shipment data creating means of the retailer D createsreceipt/shipment data with the number 310 input for the ID, a receiptdate and time input for the date and time, the retailer D input for thesite name, the wholesaler C input for the receipt/shipment destination,and receipt input for the process (step 1302).

The receipt/shipment data creating means of the retailer D sends thecreated receipt/shipment data to the traceability data center. Thecentral processing unit of the traceability data center stores thereceived receipt/shipment data in the external storage device (step1303).

The index data creating means of the retailer D reads the ID of the boxbefore the box is unpacked (step 1304).

The index data creating means of the retailer D reads the IDs of two cutmeats taken out by unpacking the box (step 1305).

The index data creating means of the retailer D creates index data withthe number 310 input for the pre-unpacking ID (Before), numbers 1001 and1002 input for the post-unpacking IDs (After), and unpacking input forthe process (step 1306).

The index data creating means of the retailer D reads the IDs of two cutmeats before the cut meat with the ID of 1001 and the cut meat with theID of 9001 are processed together into a ground meat (step 1307).

The index data creating means of the retailer D attaches a tag with theID of 11-111 to one ground meat obtained by processing two cut meatstogether (step 1308).

The index data creating means of the retailer D creates index data withnumbers 1001 and 9001 input for the pre-processing IDs (Before), thenumber 11-111 input for the post-processing ID (After), and processinginput for the process (step 1309).

The index data creating means of the retailer D sends the created indexdata to the traceability data center. The central processing unit of thetraceability data center stores the received index data in the externalstorage device (step 1310).

The receipt/shipment data creating means of the retailer D reads the IDof the ground meat being a shipped article (step 1311).

The receipt/shipment data creating means of the retailer D createsreceipt/shipment data with the number 11-111 input for the ID, ashipment date and time input for the date and time, the retailer D inputfor the site name, the consumer input for the receipt/shipmentdestination, and shipment input for the process (step 1312).

The receipt/shipment data creating means of the retailer D sends thecreated receipt/shipment data to the traceability data center. Thecentral processing unit of the traceability data center stores thereceived receipt/shipment data in the external storage device to end theprocess (step 1313). The process described above allows receipt/shipmentdata and index data to be created at sites of the producer A, processorB, wholesaler C and retailer D.

A flow of a process in which the central processing unit of thetraceability data center outputs trace-back information of the groundmeat with the ID of 11-111 received at the retailer D is shown in FIG.5.

As a condition for retrieving receipt/shipment data, the number 11-111is set for the ID, the retailer D is set for the site name, and receiptis set for the process (step 2001).

Data in which the ID is 11-111, the site name is the retailer D and theprocess is receipt is retrieved from receipt/shipment data stored in theexternal storage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 11-111, the site name is the retailer D and the processis receipt is 0 (step 2003).

As a condition for retrieving receipt/shipment data, shipment is set forthe process (step 2011).

Data in which the ID is 11-111, the site name is the retailer D and theprocess is shipment is retrieved from receipt/shipment data stored inthe external storage device of the traceability data center (step 2012).

Whether the number of hits as a result of retrieval at step 2012 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 11-111, the site name is the retailer D and the processis shipment is 1 (step 2013).

Receipt/shipment data hit at step 2013 is output as traceabilityinformation (step 2014).

As a condition for retrieving index data, the ID of 11-111 of thecondition for retrieving receipt/shipment data is set for After ID (step2015).

Data in which After ID is 11-111 is retrieved from index data of theretailer D stored in the external storage device of the traceabilitydata center (step 2016).

Whether the number of hits as a result of retrieval at step 2016 is 0,or 1 or more is checked. The number of hits of index data in which AfterID is 11-111 is 2 (step 2017).

Two index data hit at step 2017 is output as traceability information(step 2018).

Before IDs (1001 and 9001) are acquired from two index data hit at step2017 (step 2019).

As a condition for retrieving receipt/shipment data, Before IDs of 1001and 9001 acquired at step 2019 are set for the ID (step 2020).

Processes (processing) are acquired from 2 index data hit at step 2017(step 2021).

Whether the processes acquired at step 2021 are unpacking is checked.None of the processes of index data in which Before IDs are 1001 and9001 is unpacking (step 2022).

Whether the processes acquired at step 2021 are packing is checked. Noneof the processes of index data in which Before IDs are 1001 and 9001 ispacking (step 2032).

As a condition for retrieving receipt/shipment data, receipt is set forthe process (step 2040).

Data in which the ID is 1001 or 9001, the site name is retailer D andthe process is receipt is retrieved from receipt/shipment data stored inthe external storage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 1001 or 9001, the site name is the retailer D and theprocess is receipt is 0 (step 2003).

As a condition for retrieving receipt/shipment data, shipment is set forthe process (step 2011).

Data in which the ID is 1001 or 9001, the site name is the retailer Dand the process is shipment is retrieved from receipt/shipment datastored in the external storage device of the traceability data center(step 2012).

Whether the number of hits as a result of retrieval at step 2012 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 1001 or 9001, the site name is the retailer D and theprocess is shipment is 0 (step 2013).

As a condition for retrieving index data, IDs of 1001 and 9001 of thecondition for retrieving receipt/shipment data are set for After IDs(step 2015).

Data in which After ID is 1001 or 9001 is retrieved from index data ofthe retailer D stored in the external storage device of the traceabilitydata center (step 2016).

Whether the number of hits as a result of retrieval at step 2016 is 0,or 1 or more is checked. The number of hits of index data in which AfterID is 1001 is 1, and the number of hits of index data in which After IDis 9001 is 0 (step 2017).

One index data hit at step 2017 is output as traceability information(step 2018).

Before ID (310) is acquired from one index data hit at step 2017 (step2019).

As a condition for retrieving receipt/shipment data, Before ID of 310acquired at step 2019 is set for the ID (step 2020).

A process (unpacking) is acquired from one index data hit at step 2017(step 2021).

Whether the process acquired at step 2021 is unpacking is checked. Theprocess of index data in which Before ID is 310 is unpacking (step2022).

The After ID (1001) is stored in a buffer of the traceability datacenter (step 2023).

As a condition for retrieving receipt/shipment data, the process ischanged to receipt (step 2040).

Data in which the ID is 310, the site name is the retailer D and theprocess is receipt is retrieved from receipt/shipment data stored in theexternal storage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 310, the site name is the retailer D and the process isreceipt is 1 (step 2003).

Receipt/shipment data hit at step 2003 is output as traceabilityinformation (step 2004).

A receipt/shipment destination (wholesaler C) is acquired fromreceipt/shipment data hit at step 2003 (step 2005).

As a condition for retrieving receipt/shipment data, the wholesaler Cbeing the receipt/shipment destination acquired at step 2005 is set forthe name of the destination (step 2006).

Data in which the ID is 310, the site name is the wholesaler C and theprocess is receipt is retrieved from receipt/shipment data stored in theexternal storage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 310, the site name is wholesaler C and the process isreceipt is 0 (step 2003).

As a condition for retrieving receipt/shipment data, shipment is set forthe process (step 2011).

Data in which the ID is 310, the site name is wholesaler C and theprocess is shipment is retrieved from receipt/shipment data stored inthe external storage device of the traceability data center (step 2012).

Whether the number of hits as a result of retrieval at step 2012 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 310, the site name is wholesaler C and the process isshipment is 1 (step 2013).

Receipt/shipment data hit at step 2013 is output as traceabilityinformation (step 2014).

As a condition for retrieving index data, the ID of 310 of the conditionfor retrieving receipt/shipment data is set for After ID (step 2015).

Data in which After ID is 310 is retrieved from index data stored in theexternal storage device of the wholesaler C (step 2016).

Whether the number of hits as a result of retrieval at step 2016 is 0,or 1 or more is checked. The number of hits of index data in which AfterID is 310 is 1 (step 2017).

One index data hit at step 2017 is output as traceability information(step 2018).

Before ID of 501 is acquired from one index data hit at step 2017 (step2019).

As a condition for retrieving receipt/shipment data, Before ID of 501acquired from acquired at step 2019 is set for the ID (step 2020).

A process (assortment) is acquired from one index data hit at step 2017(step 2021).

Whether the process acquired at step 2021 is unpacking is checked. Theprocess of index data in which Before ID is 501 is not unpacking (step2022).

Whether the process acquired at step 2021 is packing is checked. Theprocess of index data in which Before ID is 501 is not packing (step2032).

As a condition for retrieving receipt/shipment data, receipt is set forthe process (step 2040).

Data in which the ID is 501, the site name is the retailer C and theprocess is receipt is retrieved from receipt/shipment data stored in theexternal storage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 501, the site name is the retailer C and the process isreceipt is 1 (step 2003).

Receipt/shipment data hit at step 2003 is output as traceabilityinformation (step 2004).

A receipt/shipment destination (processor B) is acquired fromreceipt/shipment data hit at step 2003 (step 2005).

As a condition for retrieving receipt/shipment data, the processor Bbeing the receipt/shipment destination acquired at step 2005 is set forthe site name (step 2006).

Data in which the ID is 501, the site name is the processor B and theprocess is receipt is retrieved from receipt/shipment data stored in theexternal storage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 501, the site name is the processor B and the process isreceipt is 0 (step 2003).

As a condition for retrieving receipt/shipment data, shipment is set forthe process (step 2011).

Data in which the ID is 501, the site name is the processor B and theprocess is shipment is retrieved from receipt/shipment data stored inthe external storage device of the traceability data center (step 2012).

Whether the number of hits as a result of retrieval at step 2012 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 501, the site name is the processor B and the process isshipment is 1 (step 2013).

Receipt/shipment data hit at step 2013 is output as traceabilityinformation (step 2014).

As a condition for retrieving index data, the ID of 501 of the conditionfor retrieving receipt/shipment data is set for After ID (step 2015).

Data in which After ID is 501 is retrieved from index data stored in theexternal storage device of the processor B (step 2016).

Whether the number of hits as a result of retrieval at step 2016 is 0,or 1 or more is checked. The number of hits of index data in which AfterID is 501 is 2 (step 2017).

Two index data hit at step 2017 are output as traceability information(step 2018).

Before IDs (1001 and 2001) are acquired from two index data hit at step2017 (step 2019).

As a condition for retrieving receipt/shipment data, Before IDs of 1001and 2001 acquired at step 2019 are set for the ID (step 2020).

Processes (packing) are acquired from two index data hit at step 2017(step 2021).

Whether the processes acquired at step 2021 are unpacking is checked.None of the processes of index data in which IDs are 1010 and 2001 isunpacking (step 2022).

Whether the processes acquired at step 2021 are packing is checked. Boththe processes of index data in which IDs are 1001 and 2001 are packing(step 2032).

After ID equal to Before ID (1001 or 2001) is retrieved from the bufferof the traceability data center. After ID (1001) is acquired, and as acondition for retrieving receipt/shipment data, only the number 1001 isset for the ID (step 2023).

As a condition for retrieving receipt/shipment data, receipt is set forthe process (step 2040).

Data in which the ID is 1001, the site name is the processor B and theprocess is shipment is retrieved from receipt/shipment data stored inthe traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 1001, the site name is the processor B and the processis receipt is 0 (step 2003).

As a condition for retrieving receipt/shipment data, shipment is set forthe process (step 2011).

Data in which the ID is 1001, the site name is the processor B and theprocess is shipment is retrieved from receipt/shipment data stored inthe external storage device of the traceability data center (step 2012).

Whether the number of hits as a result of retrieval at step 2012 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 1001, the site name is the processor B and the processis shipment is 0 (step 2013).

As a condition for retrieving index data, the ID of 1001 of thecondition for retrieving receipt/shipment data is set for After ID (step2015).

Data in which After ID is 1001 is retrieved from index data stored inthe external storage device of the processor B (step 2016).

Whether the number of hits as a result of retrieval at step 2016 is 0,or 1 or more is checked. The number of hits of index data in which AfterID is 1001 is 1 (step 2017).

One index data hit at step 2017 is output as traceability information(step 2018).

Before ID (100) is acquired from one index data hit at step 2017 (step2019).

As a condition for retrieving receipt/shipment data, Before ID of 100acquired at step 2019 is set for the ID (step 2020).

A process (dressing) is acquired from one index data hit at step 2017(step 2021).

Whether the process acquired at step 2021 is unpacking is checked. Theprocess of index data in which Before ID is 100 is not unpacking (step2022).

Whether the process acquired at step 2021 is packing is checked. Theprocess of index data in which Before ID is 100 is not packing (step2032).

As a condition for retrieving receipt/shipment data, the process ischanged to receipt (step 2040).

Data in which the ID is 100, the site name is the processor B and theprocess is receipt is retrieved from receipt/shipment stored in theexternal storage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 100, the site name is the processor B and the process isreceipt is 1 (step 2003).

Receipt/shipment data hit at step 2003 is output as traceabilityinformation (step 2004).

A receipt/shipment destination (producer A) is acquired fromreceipt/shipment data hit at step 2003 (step 2005).

As a condition for retrieving receipt/shipment data, the producer Abeing the receipt/shipment destination acquired at step 2005 is set forthe site name (step 2006).

Data in which the ID is 100, the site name is the producer A and theprocess is receipt is retrieved from receipt/shipment data stored in theexternal storage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 100, the site name is the producer A and the process isreceipt is 0 (step 2003).

As a condition for retrieving receipt/shipment data, shipment is set forthe process (step 2011).

Data in which the ID is 100, the site name is the producer A and theprocess is shipment is retrieved from receipt/shipment data stored inthe external storage device of the traceability data center (step 2012).

Whether the number of hits as a result of retrieval at step 2012 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 100, the site name is the producer A and the process isshipment is 1 (step 2013).

Receipt/shipment data hit at step 2013 is output as traceabilityinformation (step 2014).

As a condition for retrieving index data, the ID of 100 of the conditionfor retrieving receipt/shipment data is set for After ID (step 2015).

Data in which After ID is 100 is retrieved from index data of theproducer A stored in the external storage device of the traceabilitydata center (step 2016).

Whether the number of hits as a result of retrieval at step 2016 is 0,or 1 or more is checked. The number of hits of index data in which AfterID is 100 is 0 and the process is ended (step 2017).

The process described above allows the ground meat with the ID of 11-111to be traced back from the consumer to the retailer D to the wholesalerC to the processor B to the producer A to output the ID (100) of beefcattle that is a raw material.

A flow of a process in which the central processing unit of thetraceability data center outputs trace-forward information of beefcattle with the ID of 100 produced by the producer A is shown in FIG. 5.

As a condition for retrieving receipt/shipment data, the number 100 isset for the ID, the producer A is set for the site name and shipment isset for the process (step 2001).

Data in which the ID is 100, the site name is the producer A and theprocess is shipment is retrieved from receipt/shipment data stored inthe external storage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 100, the site name is the producer A and the process isshipment is 1 (step 2003).

Receipt/shipment data hit at step 2003 is output as traceabilityinformation (step 2004).

A receipt/shipment destination (processor B) is acquired fromreceipt/shipment data hit at step 2003 (step 2005).

As a condition for retrieving receipt/shipment data, the processor Bbeing the receipt/shipment destination acquired at step 2005 is set forthe site name (step 2006).

Data in which the ID is 100, the site name is the processor B and theprocess is shipment is retrieved from receipt/shipment data stored inthe external storage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 100, the site name is the processor B and the process isshipment is 0 (step 2003).

As a condition for retrieving receipt/shipment data, receipt is set forthe process (step 2011).

Data in which the ID is 100, the site name is the processor B and theprocess is receipt is retrieved from receipt/shipment stored in theexternal storage device of the traceability data center (step 2012).

Whether the number of hits as a result of retrieval at step 2012 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 100, the site name is the processor B and the process isreceipt is 1 (step 2013).

Receipt/shipment data hit at step 2013 is output as traceabilityinformation (step 2014).

As a condition for retrieving index data, the ID of 100 of the conditionfor retrieving receipt/shipment data is set for Before ID (step 2015).

Data in which Before ID is 100 is retrieved from index data stored inthe external storage device of the processor B (step 2016).

Whether the number of hits as a result of retrieval at step 2016 is 0,or 1 or more is checked. The number of hits of index data in which AfterID is 100 is 2 (step 2017).

Two index data hit at step 2017 are output as traceability information(step 2018).

After IDs (1001 and 1002) are acquired from two index data hit at step2017 (step 2019).

As a condition for retrieving receipt/shipment data, After IDs of 1001and 1002 acquired at step 2019 are set for the ID (step 2020).

Processes (dressing) are acquired from two index data hit at step 2017(step 2021).

Whether the processes acquired at step 2021 are packing is checked. Noneof the processes of index data in which After IDs are 1001 and 1002 ispacking (step 2022).

Whether the processes acquired at step 2021 are unpacking is checked.None of the processes of index data in which After IDs are 1001 and 1002is unpacking (step 2032).

As a condition for retrieving receipt/shipment data, shipment is set forthe process (step 2040).

Data in which the ID is 1001 or 1002, the site name is the processor Band the process is shipment is retrieved from receipt/shipment datastored in the external storage device of the traceability data center(step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 1001 or 1002, the site name is the processor B and theprocess is receipt is 0 (step 2003).

As a condition for retrieving receipt/shipment data, receipt is set forthe process (step 2011).

Data in which the ID is 1001 or 1002, the site name is the processor Band the process is shipment is retrieved from receipt/shipment datastored in the external storage device of the traceability data center(step 2012).

Whether the number of hits as a result of retrieval at step 2012 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 1001 or 1002, the site name is the processor B and theprocess is shipment (step 2013).

As a condition for retrieving index data, IDs of 1001 and 1002 of thecondition for retrieving receipt/shipment data are set for Before ID(step 2015).

Data in which Before ID is 1001 or 1002 is retrieved from index datastored in the external storage device of the processor B (step 2016).

Whether the number of hits as a result of retrieval at step 2016 is 0,or 1 or more is checked. The number of hits of index data in whichBefore ID is 1001 is 1, and the number of hits of index data in whichbefore ID is 1002 is 0 (step 2017).

One index data hit at step 2017 is output as traceability information(step 2018).

After ID (501) is acquired from one index data hit at step 2017 (step2019).

As a condition for retrieving receipt/shipment data, After ID of 501acquired at step 2019 is set for the ID (step 2020).

A process (packing) is acquired from one index data hit at step 2017(step 2021).

Whether the process acquired at step 2021 is packing is checked. Theprocess of index data in which After ID is 501 is packing (step 2022).

Before ID (1001) is stored in the buffer of the traceability data center(step 2023).

As a condition for retrieving receipt/shipment data, the process ischanged to shipment (step 2040).

Data in which the ID is 501, the site name is the processor B and theprocess is shipment is retrieved from receipt/shipment data stored inthe external storage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 501, the site name is the processor B and the process isshipment is 1 (step 2003).

Receipt/shipment data hit at step 2003 is output as traceabilityinformation (step 2004).

A receipt/shipment destination (wholesaler C) is acquired fromreceipt/shipment data hit at step 2003 is acquired (step 2005).

As a condition for retrieving receipt/shipment data, the wholesaler Cbeing the receipt/shipment destination acquired at step 2005 is set forthe site name (step 2006).

Data in which the ID is 501, the site name is the wholesaler C and theprocess is shipment is retrieved from receipt/shipment data stored inthe external storage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 501, the site name is wholesaler C and the process isshipment is 0 (step 2003).

As a condition for retrieving receipt/shipment data, receipt is set forthe process (step 2011).

Data in which the ID is 501, the site name is the wholesaler C and theprocess is receipt is retrieved from receipt/shipment data stored in theexternal storage device of the traceability data center (step 2012).

Whether the number of hits as a result of retrieval at step 2012 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 501, the site name is the wholesaler C and the processis receipt is 1 (step 2013).

Receipt/shipment data hit at step 2013 is output as traceabilityinformation (step 2014).

As a condition for retrieving index data, the ID of 501 of the conditionfor retrieving receipt/shipment data is set for Before ID (step 2015).

Data in which Before ID is 501 is retrieved from index data stored inthe external storage device of the wholesaler C (step 2016).

Whether the number of hits as a result of retrieval at step 2016 is 0,or 1 or more is checked. The number of hits of index data in whichBefore ID is 501 is 1 (step 2017).

One index data hit at step 2017 is output as traceability information(step 2018). After ID (310) is acquired from one index data hit at step2017 (step 2019).

As a condition for retrieving receipt/shipment data, After ID of 310acquired at step 2019 is set for the ID (step 2020).

A process (assortment) is acquired from one index data hit at step 2017(step 2021).

Whether the process acquired at step 2021 is packing is checked. Theprocess of index data in which After ID is 310 is not packing (step2022).

Whether the process acquired at step 2021 is unpacking is checked. Theprocess of index data in which After ID is 310 is not unpacking (step2032).

As a condition for retrieving receipt/shipment data, shipment is set forthe process (step 2040).

Data in which the ID is 310, the site name is the wholesaler C and theprocess is shipment is retrieved from receipt/shipment data stored inthe external storage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 310, the site name is the wholesaler C and the processis shipment is 1 (step 2003).

Receipt/shipment data hit at step 2003 is output as traceabilityinformation (step 2004).

A receipt/shipment destination (wholesaler D) is acquired fromreceipt/shipment data hit at step 22003 (step 2005).

As a condition for retrieving receipt/shipment data, the wholesaler Dbeing the receipt/shipment destination acquired at step 2005 is set forthe site name (step 2006).

Data in which the ID is 310, the site name is the retailer D and theprocess is shipment is retrieved from receipt/shipment data stored inthe external storage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 310, the site name is the retailer D and the process isshipment is 0 (step 2003).

As a condition for retrieving receipt/shipment data, receipt is set forthe process (step 2011).

Data in which the ID is 310, the site name is the retailer D and theprocess is receipt is retrieved from receipt/shipment data stored in theexternal storage device of the traceability data center (step 2012).

Whether the number of hits as a result of retrieval at step 2012 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 310, the site name is the retailer D and the process isreceipt is 1 (step 2013).

Receipt/shipment data hit at step 2013 is output as traceabilityinformation (step 2014).

As a condition for retrieving index data, the ID of 310 of the conditionfor retrieving receipt/shipment data is set for Before ID (step 2015).

Data in which Before ID is 310 is retrieved from index data of theretailer D stored in the external storage device of the traceabilitydata center (step 2016).

Whether the number of hits as a result of retrieval at step 2016 is 0,or 1 or more is checked. The number of hits of index data in whichBefore ID is 310 is 2 (step 2017).

Two index data hit at step 2017 is output as traceability information(step 2018).

After IDs (1001 and 2001) are acquired from two index data hit at step2017 (step 2019).

As a condition for retrieving receipt/shipment data, After IDs of 1001and 2001 acquired at step 2019 are set for the ID (step 2020).

Processes (unpacking) are acquired from twp index data hit at step 2017(step 2021).

Whether the processes acquired at step 2021 are packing is checked. Noneof the processes of index data in which After IDs are 1001 and 2001 ispacking (step 2022).

Whether the processes acquired at step 2021 are unpacking is checked.Both the processes of index data in which After IDs are 1001 and 2001are unpacking (step 2032).

Before ID equal to After ID (1001 or 2001) is retrieved from the bufferof the traceability data center. Before ID (1001) is acquired, and as acondition for retrieving receipt/shipment data, only the number 1001 isset for the ID (step 2023).

As a condition for retrieving receipt/shipment data, shipment is set forthe process (step 2040).

Data in which the ID is 1001, the site name is the retailer D and theprocess is shipment is retrieved from receipt/shipment data stored inthe external storage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 1001, the site name is the retailer D and the process isshipment is 0 (step 2003).

As a condition for retrieving receipt/shipment data, receipt is set forthe process (step 2011).

Data in which the ID is 1001, the site name is the retailer D and theprocess is receipt is retrieved from receipt/shipment data stored in theexternal storage device of the traceability data center (step 2012).

Whether the number of hits as a result of retrieval at step 2012 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 1001, the site name is the retailer D and the process isreceipt is 0 (step 2013).

As a condition for retrieving index data, the ID of 1001 of thecondition for retrieving receipt/shipment data is set for Before ID(step 2015).

Data in which Before ID is 1001 is retrieved from index data of theretailer D stored in the external storage device of the traceabilitydata center (step 2016).

Whether the number of hits as a result of retrieval at step 2016 is 0,or 1 or more is checked. The number of hits of index data in whichBefore ID is 1001 is 1 (step 2017).

One index data hit at step 2017 is output as traceability information(step 2018).

After ID (11-111) is acquired from one index data hit at step 2017 (step2019).

As a condition for retrieving receipt/shipment data, After ID of 11-111acquired at step 2019 is set for the ID (step 2020).

A process (processing) is acquired from one index data hit at step 2017(step 2021).

Whether the process acquired at step 2021 is packing is checked. Theprocess of index data in which After ID is 11-111 is not packing (step2022).

Whether the process acquired at step 2021 is unpacking is checked. Theprocess of index data in which After ID is 11-111 is not unpacking (step2032).

As a condition for retrieving receipt/shipment data, the process ischanged to shipment (step 2040).

Data in which the ID is 11-111, the site name is the retailer D and theprocess is shipment from receipt/shipment data stored in the externalstorage device of the traceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 11-111, the site name is the retailer D and the processis dispatch is 1 (step 2003).

Receipt/shipment data hit at step 2003 is output as traceabilityinformation (step 2004).

A receipt/shipment destination (consumer) is acquired fromreceipt/shipment data hit at step 2003 is acquired (step 2005).

As a condition for retrieving receipt/shipment data, the consumer beingthe receipt/shipment destination acquired at step 2005 is set for thesite name (step 2006). Data in which the ID is 11-111, the site name isthe consumer and the process is shipment is retrieved fromreceipt/shipment data stored in the external storage device of thetraceability data center (step 2002).

Whether the number of hits as a result of retrieval at step 2002 is 0,or 1 or more is checked. The number of hits of receipt/shipment data inwhich the ID is 11-111, the site name is the consumer and the process isshipment is 0 (step 2003).

As a condition for retrieving receipt/shipment data, receipt is set forthe process (step 2011).

Data in which the ID is 11-111, the site name is the consumer and theprocess is receipt is retrieved from receipt/shipment data stored in theexternal storage device of the traceability data center (step 2012).

Whether the number of hits as a result at step 2012 is 0, or 1 or moreis checked. The number of hits of receipt/shipment data in which the IDis 11-111, the site name is the consumer and the process is receipt is 0(step 2013).

As a condition for retrieving index data, the ID of 11-111 of thecondition for retrieving receipt/shipment data is set for Before ID(step 2015).

Data in which Before ID is 11-111 is retrieved from index data of theconsumer stored in the external storage device of the traceability datacenter (step 2016).

Whether the number of hits as a result of retrieval at step 2016 is 0, 1or more is checked. The number of hits of index data in which Before IDis 11-111 is 0, and the process is ended (step 2017).

The process described above allows beef cattle with the ID of 100 to betraced back from the producer A to the processor B to the wholesaler Cto the consumer to output the name of the site at which the product ofwhich the raw material is the beef cattle with the ID of 100 currentlyexists.

Example 2

In this example, a mode for carrying out the present invention whenarticles cannot be traced using time information because process historydata sent from each site has no or incorrect time information and thusthe process history data is sent in an order different from that for theactual process in Example 1 will be described.

In this example, as shown in FIG. 3, the trace object is a meat, andsites are a plurality of processors (A, B, C, D) dressing beef cattleinto cut meats, a plurality of wholesalers (A, B, C, D) assorting cutmeats for retailers, and a plurality of retailers (A, B, C, D)processing a plurality of cut meats together into a ground meat. In theprocessor B, boxes with IDs of 501 and 502 are shipped to the wholesalerC. In the wholesaler C, the boxes with IDs of 501 and 502 are receivedfrom the processor B, a tag with the ID of 310 is attached to the boxwith the ID of 501 for assortment, and the box with the ID of 310 isshipped to the retailer D. The box with the ID of 502 is shipped to theretailer A. The box with the ID of 310 is received from the wholesaler Cin the retailer D, and the box with the ID of 502 is received from thewholesaler C in the retailer A.

In this example, configurations in common with Example 1 are notdescribed.

FIG. 6 is a block diagram showing a system of this example. The systemcomprises a traceability data center 100, a processor B200 b dressingbeef cattle into cut meats, a wholesaler C200 c assorting cut meats forretailers, a retailer D200 d processing a plurality of cut meatstogether into a ground meat, a retailer A200 a, and a network 900 suchas a telephone line, a LAN and a dedicated line. The traceability datacenter 100 collects information required for traceability from a site200 and outputs trace-back information and trace-forward information tooutside, and comprises communication devices 110 such as a modem, arouter and a terminal adapter, a central processing unit 120 such as aCPU, output devices 130 such as a display, a printer, a FAX and anelectronic data output, and an external storage device 160 such as ahard disk. The processor B200 b, the wholesaler C200 c, the retailerD200 d and the retailer A200 a manage a trace object duringreceipt/shipment and processing, and comprise communication devices 210(a, b, c, d) such as modems, routers, terminal adapters and FAX, centralprocessing units 220 (a, b, c, d) such as CPUs, input devices 230 (a, b,c, d) such as keyboards and touch panels, mono ID discriminating devices250 (a, b, c, d) such as barcode readers, two-dimensional code readersand RFID readers, and external storage devices 260 (a, b, c, d) such ashard disks. The traceability data center 100, the processor B200 b, thewholesaler C200 c, the retailer D200 d and the retailer A200 a areinterconnected via the network 900 using the communication devices (a,b, c, d).

FIG. 7 shows one example of process history data 22 which is output atsites 200. The process history data 22 stores history data of processingof a trace object. Process history data 22 b is process history datawhich is output during the shipment process at the processor B, has anitem of a mono ID related to the trace object, an item of a date andtime on which the trace object was shipped, an item of the name of asite from which the trace object was shipped, an item of the name of asite to which the trace object is shipped, and an item of the type ofprocess, and is output by, for example, a shipment managing system inthe processor B. Process history data 22 c is process history data whichis output during the assortment process at the wholesaler C, has an itemof a mono ID related to the trace object before assortment, an item of amono ID related to the trace object after assortment, an item of a dateand time on which the trace object was assorted, an item of the name ofa site at which the trace object was assorted, and an item of the typeof process, and is output by, for example, an assortment managing systemin the wholesaler C. Process history data 22 a is process history datawhich is output during the shipment process at the wholesaler C, has anitem of a mono ID related to the trace object, an item of a date andtime on which the trace object was shipped, an item of the name of asite from which the trace object was shipped, an item of the name of asite to which the trace object is shipped, and an item of the type ofprocess, and is output by, for example, a shipment managing system inthe wholesaler C.

FIG. 8 shows one example of process history data 11 managed at thetraceability center 100. The process history data 11 has an item of aprocess ID for uniquely managing a process, an item of a mono ID relatedto the trace object, an item of a date and time on which the traceobject was processed, an item of the name of a site at which the traceobject was processed, and an item of the type of process.

FIG. 9 shows one example of index data 12 managed at the traceabilitycenter 100. The index data 12 is data indicating a relation between apre-process ID before a process, such as processing or packing, of thetrace object in the site and a post-process ID, and has the pre-processID (Before) and the post-process ID (After).

A flow of a process for creating process history data 22 in each site200 is shown in FIG. 10. As preparation, the site name is determinedfrom the input device 230 and stored in the external storage device 260.If this process is carried out at the wholesaler C200 c, for example,the “site name” is determined to be the “wholesaler C” (step 4101).

The central processing unit 220 of the site 200 determines the type ofprocess from the input device 230 before the trace object is processed.The type of process is, for example, “shipment”, “assortment” or thelike. If “assortment” is selected, processing proceeds to step 4111, andif “shipment” is selected, processing proceeds to step 4121 (step 4102).

If “assortment” is selected at step 4102, a mono ID related to the traceobject is discriminated using the mono ID discriminating device 250. Inthis case, the “mono ID” is “501” (step 4111).

A new mono ID is given to the trace object according to an assortmentinstruction or the like. In this case, “310” is newly given to the traceobject with the “mono ID” of “501” (step 4112).

Then, process history data 22 is created from information of steps 4101to 4112, and stored in the external storage device 260. In this case,process history data 22 c of FIG. 7 is created (step 4113).

If “shipment” is selected at step 4102, a mono ID related to the traceobject is discriminated using the mono ID discriminating device 250. Inthis case, the “mono ID” is “310” (step 4121).

Then, a shipment destination is input from the input device 230according to a shipment instruction or the like (step 4122).

Then, process history data 22 is created from information of steps 4101to steps 4122, and stored in the external storage device 260. In thiscase, process history data 22 a of is created (step 4123).

A user makes a selection on whether process history data 22 stored inthe external storage device 260 is sent to the traceability center 100.Processing proceeds to step 4132 if YES, and processing proceeds to step4102 if NO (step 4131).

If YES at step 4131, the central processing unit 220 sends processhistory data 22 to the traceability data center 100 using thecommunication device 210, and ends the process for creating processhistory data 22 at the site 200 (step 3107).

The process for creating process history data 22 at the site 200 as beendescribed.

Then, a flow of a process for creating and storing process history data11 and index data 12 at the traceability data center 100 is shown inFIG. 11.

The central processing device 120 of the traceability data center 100receives process history data 22 sent from each site 200 using thecommunication device (step 4201).

The item of the process of the received process history data 22 isexamined. The process is, for example, “shipment”, “assortment” or thelike. If the process is “assortment”, processing proceeds to step 4211,and if the process is “shipment”, processing proceeds to step 4221 (step4202).

If the process of process history data 22 is “assortment” at step 4202,one assortment process history data 22 is divided into pre-assortmentand post-assortment two process history data such that they have onemono ID.

For the item of the mono ID, at this time, the value of the item of thepre-assortment mono ID of process history data 22 is set for one data,and the value of the post-assortment mono ID of process history data 22is set for the other data. Same values are set for the item of the dateand time, the item of the site name and the item of the process. Forexample, process history data 22 c of FIG. 7 has two mono IDs, andtherefore as in records with “process IDs” of “123456-05” and“123456-06” in process history data of FIG. 8, the “mono ID” is dividedinto “501” and “310”, and same values are set for the “date and time”,the “site name” and the “process” (step 4211).

If the item of the process of process history data 22 is “shipment” atstep 4202, one assortment process history data 22 is divided into twoprocess history data: shipment process and receipt process, such thatthey have one mono ID. For the item of the mono ID, at this time, thesame value is set for both data. For the item of the date and time, thevalue of the item of the date and time of process history data 22 is setfor one data, and a blank is set for the other data. For the item of thesite name, the value of the item of the site name of process historydata 22 is set for one data, and the value of the item of the shipmentdestination of process history data 22 is set for the other data. Forthe item of the process, “shipment” is set for one data, and “receipt”is set for the other data. For example, the record with the “mono ID” of“310” in process history data 22 a of FIG. 7 has two site names, andtherefore as in records with “process IDs” of “123456-07” and“123456-08” in process history data 11 of FIG. 8, the “wholesaler C” andthe “retailer D” are set for the “site name”, “04/15 11:00” and a blankare set for the “date and time”, “shipment” and “receipt” are set forthe “process”, and the same value is set for the “mono ID” (step 4221).

Then, numbers are assigned to the item of the process ID sequentially inorder of reception for process history data 11 (step 4231).

Process history data 11 created at step 4231 is stored in the externalstorage device 160 of the traceability data center 100 (step 4232).

For mutually relating two process history data 11 divided at step 4211or step 4221 and having numbers assigned to process IDs at step 4231,the pre-process ID is stored for the item of Before of index data 12,the post-process ID is stored for the item of After, and the index data12 is stored in the external storage device 160 of the traceability datacenter 100 (step 4233). For example, for process history data 22 of FIG.7, “123456-05” is set for the item of Before of index data 12, and“123456-06” is set for the item of After because the “process ID” ofprocess history data 11 of FIG. 8 is divided into records of “123456-05”and “123456-06”.

Then, one “mono ID” and one “site name” are designated from processhistory data 11 to extract “process IDs” of records having same valuesfor both the items (step 4234). For example, if “310” is designated forthe “mono ID” and the “wholesaler C” is designated for the “site name”from process history data, “process IDs” of “123456-06” and “123456-07”are extracted.

If there are two or more process IDs which are extracted at step 4234,then processing proceeds to step 4236, and if there is no process ID orone process ID which is extracted, the process for creating and storingprocess history data 11 and index data 12 is ended (step 4235).

If YES at step 4235, “process IDs” are arranged in ascending order,lower process IDs are stored for the item of Before of index data 12 andnext lower process IDs are stored for the item of After in analternative fashion, and the index data 12 is stored in the externalstorage device 160 of the traceability data center 100 (step 4236). Forexample, if “process IDs” of “123456-06” and “123456-07” are extracted,“123456-06” is set for the item of Before of index data 12, and“123456-07” is set for the item of After.

The process for creating and storing process history data 11 and indexdata 12 in the traceability data center 100 has been described.

A flow of a process for outputting trace information of the trace objectis shown in FIG. 12.

The central processing unit 120 of the traceability data center 100extracts data matching the “mono ID” of a targeted trace object and the“site name” at which tracing is started from process history data 11stored in the external storage device 160. For example, if the “mono ID”of the targeted trace object is “501” and the “site name” is the“processor B”, a record in which the “mono ID” is “501” and the “sitename” is the “processor B” is extracted from process history data 11 ofFIG. 8 (step 4301). In this case, the record with the “process ID” of“123456-01” is extracted.

Then, the central processing unit 120 retrieves the process ID extractedat step 4301 from the item of Before of index data 12. Values of itemsof After corresponding to values of items of Before of index data 12 areretrieved from the item of Before. This process is repeated until thereis no retrieved result (step 4302). For example, “123456-01” isretrieved from the item of Before of index data 12. The value of theitem of After of hit data is “123456-03”. Then, “123456-03” is retrievedfrom the item of Before. The value of the item of After of hit data is“123456-05”. Then, “123456-05” is retrieved from the item of Before. Thevalue of the item of After of hit data is “123456-06”. “123456-06” isretrieved from the item of Before. The value of the item of After of hitdata is “123456-07”. Then, “123456-07” is retrieved from the item ofBefore. The value of the item of After of hit data is “123456-08”.

Then, the central processing unit 120 sequentially extracts “processIDs” hit at step 4302 from process history data 11 (step 4303). In thiscase, the “process IDs” are rearranged in the order of “123456-01”,“123456-03”, “123456-05”, “123456-06”, “123456-07” and “123456-08”.

The central processing unit 120 outputs to the output device 130 traceinformation indicating that the trace object with the “mono ID” of “501”was processed in the order of the “processor B”, the “wholesaler C” andthe “retailer D” from the result of step 4303, and ends the process.

In this way, the user can trace the trace object.

Example 3

In this example, a mode for carrying out the present invention when noindex data is required in Example 2 will be described.

In this example, as shown in FIG. 3, the trace object is a meat, sitesare a plurality of processors (A, B, C, D) dressing beef cattle into cutmeats, a plurality of wholesalers (A, B, C, D) assorting cut meats forretailers, and a plurality of retailers (A, B, C, D) processing aplurality of cut meats together into a ground meat. In the processor B,a box with the ID of 502 is shipped to the wholesaler C. In thewholesaler C, the box with the ID of 502 is received from the processorB, and the box with the ID of 502 is shipped to the retailer A. In theretailer A, the box with the ID of 502 is received from the wholesalerC.

In this example, configurations in common with Example 2 are notdescribed.

The process for creating process history data 22 at each site 200 is notdescribed because it is in common with Example 2.

A flow of a process for creating and storing process history data 11 atthe traceability data center 100 will be described using FIG. 11.

The central processing unit 120 of the traceability data center 100receives process history data 22 sent from each site 200 using thecommunication device 110 (step 4201).

The item of the process of received process history data 22 is examined.In this example, only “shipment” is covered, and therefore processingproceeds to step 4221 (step 4202).

If the item of the process of process history data 22 is “shipment” atstep 4202, one assortment process history data 22 is divided into twoprocess history data: shipment process and receipt process, such thatthey have one mono ID. For the item of the mono ID, at this time, thesame value is set for both data. For the item of the date and time, thevalue of the item of the date and time of process history data 22 is setfor one data, and a blank is set for the other data. For the item of thesite name, the value of the item of the site name of process historydata 22 is set for one data, and the value of the item of the shipmentdestination of process history data 22 is set for the other data. Forthe item of the process, “shipment” is set for one data, and “receipt”is set for the other data. For example, the record with the “mono ID” of“502” in process history data 22 a of FIG. 7 has two site names, andtherefore as in records with “process IDs” of “123456-09” and“123456-10” in process history data 11 of FIG. 8, the “wholesaler C” andthe “retailer A” are set for the “site name”, “04/15 12:00” and a blankare set for the “date and time”, “shipment” and “receipt” are set forthe “process”, and the same value is set for the “mono ID” (step 4221).

Then, numbers are assigned to the item of the process ID sequentially inorder of reception for process history data 11 (step 4231).

Process history data 11 created at step 4231 is stored in the externalstorage device 160 of the traceability data center 100 (step 4232).

The process for creating and storing process history data 11 at thetraceability data center 100 has been described.

A flow of a process for outputting trace information of the trace objectis shown in FIG. 13.

The central processing unit 120 of the traceability data center 100extracts data matching the “mono ID” of a targeted trace object fromprocess history data 11 stored in the external storage device 160. Forexample, if the “mono ID” of the targeted trace object is “502”, onlyrecords with the “mono ID” of “502” are extracted from process historydata 11 of FIG. 8 (step 3301). In this case, records with “process IDs”of “123456-02”, “123456-04”, “123456-09” and “123456-10” are extracted.

Then, the central processing unit 120 compares the values of “processIDs”, and rearranges them in ascending order (step 3302). In this case,the “process IDs” are rearranged in the order of “123456-02”,“123456-04”, “123456-09” and “123456-10”.

The central processing unit 120 outputs to the output device 130 traceinformation indicating that the trace object with the “mono ID” of “502”was processed in the order of the “processor B”, the “wholesaler C” andthe “retailer A from the result of step 3302, and ends the process.

In this way, the user can trace the trace object.

Example 4

Example 4 of the present invention will now be described. This examplecovers the case where information schemes manipulated by informationprocessing apparatuses in sites, i.e. the producer A, the processor B,the wholesaler C and the retailer D are different. Usually, ininformation processing apparatuses that are used in sites, schemes(format, item name, etc.) manipulated by the apparatuses are often notthe same (particularly, schemes may be different among producers). Ifindividual article information with data sent to the traceability datacenter from the producer A and the processor B having different schemesis recorded directly, the following problems may arise. For example,same individual articles are treated as different individual articles,and for items included in individual article information, differentitems are associated with each other, and same items are treated asdifferent items. The problems are solved in this example. For thispurpose, in this example, one of individual article information storedin the traceability center (traceability information) and individualarticle information sent from each site is converted to suit the otherin accordance with a predetermined rule of individual articleinformation. This eliminates necessity to convert individual articleinformation into intermediate information common to each individualarticle information to be managed, and also eliminates necessity toconvert all individual article information, thus making it possible toreduce a number of operations in information processing.

In a first method thereof, sent individual article information issequentially converted to suit stored individual article information(traceability information). In a second method, sent individual articleinformation is compared with stored individual article information, andindividual article information is converted to suit informationincluding all items of the individual article information. The method ismore effective for articles, such as industrial products, in which thenumber of added items is larger in later steps. As a third method, thenumbers of items included in individual article information arecompared, and individual article information having a smaller number ofitems is converted to suit individual article information having alarger number of items.

First, the first method will be described.

First, at step 601, the producer A sends individual article informationA shown in FIG. 14, tag indemnification information for identifying atag (or individual article) recorded in a tag attached to the individualarticle, identification information A for identifying the producer A,and scheme information A indicating an information scheme in theproducer A to the traceability center. That is, as individual articleinformation A, an individual article ID “001” for identifying theindividual article, a level “rank 1” indicating quality of theindividual article, an examination date “January 1, 00”, an examinationresult “good” and a shipment date “January 3, 00) are sent to thetraceability center.

Then, at step 602, the traceability center receives the information.Step 603, a traceability database is searched using tag identificationinformation.

If traceability information corresponding to tag identificationinformation does not exist, individual article information sent asinitial information is associated with tag identification informationand identification information A, and recorded in the traceabilitydatabase as traceability information at step 604.

If traceability information corresponding to tag identificationinformation exists, processes same as those of step 607 and subsequentsteps are carried out.

Then, at step 605, the processor B sends individual article informationB, tag identification information, identification information B foridentifying the processor B, and scheme information B indicating theinformation scheme in the processor B.

Then, at step 606, the traceability center searches the traceabilitydatabase using tag identification information. If it is detected thatindividual article information A sent from the producer A is stored as aresult, a conversion rule database is searched using scheme informationA and scheme information B to check whether a conversion rule forconverting the information exists at step 607.

If the conversion rule exits, information is converted in accordancewith the conversion rule, and the converted information is stored in thetraceability database at step 608. In this case, the names of items arefirst converted into the names of corresponding traceability items(names of items of individual article information A). Specifically, the“individual article ID” is unchanged, the “class” is converted into the“level”, the “inspection date” is converted into the “examination date”,the “inspection result” is converted into the “examination result”, andthe “sale date” is converted into the “shipment date”. The “name of theindividual article” is deleted because it is not used in this example.Then, the record order of items of individual article information A ofwhich the names have been changed is changed to suit traceability items.Because items corresponding to the “processing description” and the“processing date” of individual article information B do not exist, thenames of these items are unchanged and added to traceabilityinformation.

Then, if the conversion rule does not exist, a process is carried out asfollows at step 609. First, items (individual article identifier, nameof individual article, class, inspection date, inspection result,processing description, processing date and sale date) included inindividual article information B are extracted. Then, traceabilitycenter items recorded in advance are compared with the extracted items.If there are matching items, data of the extracted items are recorded incorresponding records. If all the extracted items are recorded in thisway, the process is ended. If unrecorded items remain, traceabilitycenter items and remaining items (in this example, every extracted itembecause there is no matching item) are output to a display apparatus ofthe traceability center to provide display encouraging the user toassociate traceability items with remaining items.

At step 610, data of remaining items are recorded in associated recordsin response to association by input from the user.

Associated results are recorded as the conversion rule. Whentraceability center items and remaining items are output to the displayapparatus, traceability center items and remaining items may beassociated with each other and output if they include partially matchingterms.

Traceability information converted in this way at step 609 and 610 isrecorded as follows. The traceability information is associated withpreviously recorded traceability information from the producer A andrecorded. The traceability information is recorded with an “explicitstatement” that the “individual article ID”, the “level”, the“examination date”, the “examination result” and the “shipment date”,which are the names of items, correspond to the scheme information A andthe “processing description” and the “processing date” correspond toscheme information B (as shown in FIG. 15).

Then, at step 611, the wholesaler C sends individual article informationC, tag identification information, identification information C foridentifying the wholesaler C, and scheme information C indicating theinformation scheme in the wholesaler C to the traceability center.

In the traceability center, the information is received at step 612. Atstep 613, processes same as those of steps 606 to 611 are carried outfor received information. However, there are some different processes,which will be described. Whether individual article informationconsisting of tow or more scheme information is stored is determined asa result of search same as that at step 606. If it is determined thatthe stored individual article information consists of two or more schemeinformation (i.e. scheme information A and B), conversion for suitingindividual article information C to individual article information A,and conversion for suiting individual article information C toindividual article information B are performed, respectively, andconverted information is merged and registered.

The second method will now be described in which sent individual articleinformation is compared with stored individual article information, andindividual article information is converted to suit individual articleinformation including all items of the individual article information.Scheme information B sent at step 605 is compared with stored schemeinformation A to determine whether one is included in the other. Forexample, which scheme information includes items of individual articleinformation corresponding to the scheme information may be recorded.Furthermore, items may be included in scheme information, and comparedto make a determination.

In the third method, Scheme information B sent at step 605 is comparedwith stored scheme information A to compare recorded individual articleinformation (traceability information) and received individual articleinformation, and individual article information having a smaller numberof items is converted to suit individual article information having alarger number of items.

In the second and third methods, traceability information should becompared with individual article information each time when individualarticle information is received from each site. Thus, for saving thetime and effort for the comparison, the process may be carried out asfollows.

At step 601, the producer A sends distribution route informationindicating the processor B, the wholesaler C, the retailer D and adistribution route, in addition to the information described above. Inthe traceability center, the above process is carried out, and thedistribution route information and the above comparison result orconversion description are associated with each other and stored. Whendistribution route information is received from the producer A nexttime, individual article information to be converted is determined basedon the stored description.

If further the second and third methods are used, many kinds oftraceability information can be stored. In this case, storedtraceability information may be converted by the method described above.

A process will now be described where no tag is used, or no tagidentification information is recorded in the tag. At steps 601 and 602,the traceability center sends an individual article informationidentifier corresponding to individual article information A in responseto the above reception. In the producer A, the received individualarticle information identifier is strung to the individual article to bemanaged. For example, if the tag is writable, the individual articleinformation identifier is written in the tag. The individual articleinformation identifier may be written in the individual article. In theprocessor B and subsequent sites, the individual article informationidentifier is sent to the traceability center. In this case, theindividual article information identifier may be sent together withindividual article information and the like.

It should be further understood by those skilled in the art thatalthough the foregoing description has been made on embodiments of theinvention, the invention is not limited thereto and various changes andmodifications may be made without departing from the spirit of theinvention and the scope of the appended claims.

1. An individual article management system for managing an individualarticle distributed through a plurality of sites with a form thereofchanged at least one of said plurality of sites, comprising: informationprocessing apparatuses installed at said plurality of sites; and a datacenter apparatus connected to each of said information processingapparatuses through a network, wherein each of said informationprocessing apparatuses, reads identification information regarding saidindividual article from a tag attached to said individual article, formsindex data including change information showing a process to saidindividual article at the corresponding site for said individualarticle, and transmits said read identification information and saidformed index data to said data center apparatus through said network,and said data center apparatus, receives said transmitted identificationinformation and said transmitted index data, and stores each of saidreceived index data into a storing apparatus so as to be associated witheach other on the basis of the identification information foridentifying said individual article.
 2. The individual articlemanagement system according to claim 1, wherein said identificationinformation is a mono ID for identifying said individual article.
 3. Theindividual article management system according to claim 2, wherein saiddata center apparatus receives, as said identification information,pre-process identification information added to said individual articleat a site before the concerned site and post-process identificationinformation added if said individual article is processed, as saidprocess, to change the form thereof at the concerned site, and storessaid pre-process identification information and said post-processidentification information into said storing apparatus so as to beassociated with said change information.
 4. The individual articlemanagement system according to claim 1, wherein said change informationincludes at least one division to divide the individual article into aplurality of articles, change to change the form or name of theindividual article, and integration to integrate a plurality ofindividual articles as said process.
 5. The individual articlemanagement system according to claim 4, wherein said individual articleis a meat, and said change information includes dressing into the meatand packing of the meat as said process.
 6. The individual articlemanagement system according to claim 3, wherein said post-processidentification information is created from said pre-processidentification information in accordance with a predetermined rule. 7.The individual article management system according to claim 6, whereinsaid pre-process identification information is expressed by a numericalvalue of a predetermined number of digits, and in said predeterminedrule, said post-process identification information is created by addinga numerical value of a predetermined number of digits to saidpre-process identification information.
 8. The individual articlemanagement system according to claim 4, wherein said data centerapparatus stores any one of the tags attached to the individual articlesbefore the integration as being active into said storing apparatus, ifsaid change information indicates said integration.
 9. The individualarticle management system according to claim 1, wherein saididentification information is a process ID for identifying each processfor said individual article.